|
Services Involved |
Impacts |
Response |
|
Services MAY include any of the following: Away Market Destination, Brokerplex Drop Copy, DAS (order sending firm), Drop Copy (for order sending firm), FSD (order sending firm), Regulatory Drop Copy (for IBs). Service Types MAY include any of the following: AMD, BDC, DPB, DCSF, FSD, RDC |
During Off-Trading and Trading Hours: - No trading suspension considerations necessary. OSFs and vendors are responsible for
supporting alternative connectivity if primary connectivity options are not
available. -Any messaging supported by the applications involved will not be processed as expected. There is always a potential for lost messages being in transit at the point of failure. -IB messages routed to AMDs should reject back to Brokerplex. -IB messages routed to BDCs should queue. -OSF orders sent from DPB firms to Matching Engines should queue on their side. Open orders already sent will either remain open or be canceled per DPB configurations. -Drop copies from Matching Engines to DCSF firms should be queued and/or resent via 29west data stores. -OSF orders sent from FSD firms to Matching Engines or IBs should queue on their side. Open orders already sent will remain open. -Regulatory drop copies from vendors to IBs should queue on their side. |
- Notify Tech Services for server and/or NAT change
support. - Notify affected firms. - Notify EXECUTIVE. - Move all applications to DR nodes with cooperation of
Technical Services and necessary NAT changes. - All hosts are pre-defined. - No configuration changes necessary. - All Fix Engine files need to be moved ahead of any
service restarts. Restart order (as applicable by server): DPB, FSD, DCSF, RDC, AMD, BDC - Confirm all data accounted for around move. SEE APPLICATION SPECIFIC RECOVERY DOCUMENTATION FOR MORE INFORMATION, IF NEEDED. |